Skip to content

docs: clarify repo topology and connected surfaces#1

Open
mdheller wants to merge 3 commits intomainfrom
docs/repo-topology-role-20260328
Open

docs: clarify repo topology and connected surfaces#1
mdheller wants to merge 3 commits intomainfrom
docs/repo-topology-role-20260328

Conversation

@mdheller
Copy link
Copy Markdown
Member

@mdheller mdheller commented Apr 7, 2026

Summary

Clarifies that SourceOS is the immutable substrate in the Linux-side topology and names the adjacent integration, contract, automation, and public-surface repos.

Why

This repo is central to the stack, but the README did not yet say how it fits with the spine, contract, and commons lanes. This update makes those boundaries explicit.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the README to clarify where this repository sits in the broader SourceOS/SociOS Linux-side topology, explicitly describing its role as the immutable OS substrate and naming adjacent integration/contract/automation/public-surface repositories.

Changes:

  • Added a “Topology position” section describing this repo’s role in the stack.
  • Listed connected repositories/surfaces and clarified what is explicitly out of scope for this repo.
  • Documented intended semantic direction for publishing a substrate-focused repo descriptor referencing sourceos-spec.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@mdheller
Copy link
Copy Markdown
Member Author

mdheller commented Apr 9, 2026

@copilot fix failed checks and conflicts

Copy link
Copy Markdown

Copilot AI commented Apr 9, 2026

@copilot fix failed checks and conflicts

Fixed in bb2adda. The CI was failing due to yamllint errors in spec/volumes/volumes.yml — alignment spaces after colons and commas (e.g. Desktop: {path: "~/Desktop", policy:) violated the [colons] and [commas] rules. Removed the extra alignment padding. No merge conflicts were found in the branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants